home *** CD-ROM | disk | FTP | other *** search
- Path: news1.h1.usa.pipeline.com!usenet
- From: grantp@usa.pipeline.com(Pete)
- Newsgroups: comp.lang.c++
- Subject: Re: Borland C++ 3.1 in Win95 ?
- Date: 2 Feb 1996 11:26:16 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4essco$amv@news1.usa.pipeline.com>
- NNTP-Posting-Host: pipe10.h1.usa.pipeline.com
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete)
- X-Newsreader: Pipeline USA v3.3.0
-
- On Feb 02, 1996 04:49:49 in article <Borland C++ 3.1 in Win95 ?>,
- 'bunyip@netspace.net.au (Adrian J.F. Land)' wrote:
-
-
- >Hi There..
- >
- >I have just got Borland C++ 3.1 and am having a few problems
- >getting it to work under Windows 95.
- >
- >When I try to compile any of the demo code, I get:
- >
- >Fatal ..\OWL\INCLUDE\OWL.H 40: Error directive: OWL applications must be
- built
- >
- >with either WIN30 or WIN31 defined.
- >
- >Does this mean Win95 is the problem? If so, is there anything that I can
-
- >upgrade to get it working?
- >
- No. Try defining WIN31. You should be able to do it via
- compiler options -- it's been a long time since BC31, I don't
- remember the steps -- or you can define it in your source
- code:
-
- #define WIN31
- #include <owl.h>
- #include <otherowlfiles.h>
-
- Reason: There were major changes in the Windows 3.0 ->
- 3.1 upgrade. New API functions were added and some were
- changed. In order for OWL to know whether or not it can
- use the Win 3.1 enhancements, the system needs to know
- that you're not developing for the 3.0 platform. In Win95,
- 16-bit Windows programs can use the 3.1 API.
-
- --
- Pete Grant
- Kalevi, Inc.
- Object Oriented Software Development
-